Single shards APIs should fail if routing is required. #4506
Assignees
Labels
Comments
ghost
assigned
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Dec 19, 2013
…in the mapping. This change make single shard requests fail when no routing is specified and routing has been configured to be required in the mapping. This change affects the following APIs: get, mget, explain, termvector, multi term vector and exists. Closes elastic#4506
honzakral
added a commit
that referenced
this issue
Jan 2, 2014
brusic
pushed a commit
to brusic/elasticsearch
that referenced
this issue
Jan 19, 2014
…in the mapping. This change make single shard requests fail when no routing is specified and routing has been configured to be required in the mapping. Thi Closes elastic#4506
brusic
pushed a commit
to brusic/elasticsearch
that referenced
this issue
Jan 19, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If routing for a specific type is configured to be required, but no routing is specified during a single shard api call a client error should be thrown. The following APIs need this validation: get, mget, explain, termvector, multi term vector and exists.
Note: this validation already happens in the index and delete APIs, but the error will change to a client error instead of the internal server error.
The text was updated successfully, but these errors were encountered: